Sourced from @​radixdlt/babylon-gateway-api-sdk's releases.

1.4.0

Overview

This is the v1.4.0 release for the Gateway. API docs are on Redocly here: https://radix-babylon-gateway-api.redoc.ly/

License

The Babylon Gateway code is released under the Radix License. Binaries/Executable components are licensed under the Radix Software EULA.

Notes for Gateway runners

[!CAUTION] This release MUST NOT be upgraded onto your existing Network Gateway installation as it has an incompatible database schema. There’s no database migration available. What it means is that this release MUST be deployed with an empty (wiped out) database. This will result in a lengthy (approx. 4 - 16 hours depending on your infrastructure) process of resynchronization. During the resynchronization majority of the GW API endpoints will not be available.

[!TIP] In the upcoming weeks we’ll release the next release (probably: 1.5.0) which will also require full ledger resynchronization.

What’s new?

• Dropped internal balance_changes fallback mechanism. As of right now this information is ingested as part of regular transaction ingestion process.
• Reworked internal mechanism used to fetch network configuration. Is no longer stored in the underlying database and it is shared across all services.
• Reworked (partially) internal mechanism used to ingest ledger data by Data Aggregator to improve maintainability and simplify future extensions.
• Fixed state_version-based ledger state at_ledger_state/from_ledger_state constraints which could result in inaccurate lookups previously. Attempt to read from non-existent state version will result in HTTP 400 Bad Request. Previously the nearest state version would be used.

API Changes

• Return components effective role assignments only for assigned modules.
• Added new filters for the /stream/transactions endpoint: accounts_with_manifest_owner_method_calls, accounts_without_manifest_owner_method_calls and manifest_class_filter.
• Extended response models returned by /transaction/committed-details and /stream/transactions endpoints:
  • added manifest_instructions optional property and a corresponding opt-in for returning original manifest of user transactions,
  • added optional manifest_classes property: a collection of zero or more manifest classes ordered from the most specific class to the least specific one.
• Added permanently_rejects_at_epoch to /transaction/status response for pending transactions.
• Added new endpoint /state/key-value-store/keys/ that allows iterating over KeyValueStore keys.

Database changes

• Created new key_value_store_aggregate_history table which will hold pointers to all key_value_store keys.
• Dropped network_configuration table.
• Fixed component's method royalty aggregation, added missing component_method_royalty_aggregate_history table.
• Changed IX_validator_emission_statistics_validator_entity_id_epoch_num~ index to include proposals_made and proposals_missed columns in order to optimize /statistics/validators/update endpoint.

Deprecations

• Obsoleted incorrectly named access_rules_package in favor of role_assignment_module_package on NetworkConfigurationResponse.well_known_addresses. Obsoleted property will contain effective copy of the new one for backwards compability.

Note to Integrators

Please note that the Babylon Core API on the Node is more powerful than on Olympia.

Integrators looking to prepare for the Radix Babylon launch should start by considering if running their own node and using the Core API would work instead of running a Gateway and using the Gateway API.

Please see the guide for integrators here.

... (truncated)

Sourced from @​radixdlt/babylon-gateway-api-sdk's changelog.

1.4.0

Release built: 08.02.2024

• Dropped internal balance_changes fallback mechanism. As of right now this information is ingested as part of regular transaction ingestion process.
• Reworked internal mechanism used to fetch network configuration. Is no longer stored in the underlying database and it is shared across all services.
• Reworked (partially) internal mechanism used to ingest ledger data by Data Aggregator to improve maintainability and simplify future extensions.
• Fixed state_version-based ledger state at_ledger_state/from_ledger_state constraints which could result in inaccurate lookups previously. Attempt to read from non-existent state version will result in HTTP 400 Bad Request. Previously the nearest state version would be used.

API Changes

• Return components effective role assignments only for assigned modules.
• Added new filters for the /stream/transactions endpoint: accounts_with_manifest_owner_method_calls, accounts_without_manifest_owner_method_calls and manifest_class_filter.
• Extended response models returned by /transaction/committed-details and /stream/transactions endpoints:
  • added manifest_instructions optional property and a corresponding opt-in for returning original manifest of user transactions,
  • added optional manifest_classes property: a collection of zero or more manifest classes ordered from the most specific class to the least specific one.
• Added permanently_rejects_at_epoch to /transaction/status response for pending transactions.
• Added new endpoint /state/key-value-store/keys/ that allows iterating over KeyValueStore keys.

Database changes

• Created new key_value_store_aggregate_history table which will hold pointers to all key_value_store keys.
• Dropped network_configuration table.
• Fixed component's method royalty aggregation, added missing component_method_royalty_aggregate_history table.
• Changed IX_validator_emission_statistics_validator_entity_id_epoch_num~ index to include proposals_made and proposals_missed columns in order to optimize /statistics/validators/update endpoint.

Deprecations

• Obsoleted incorrectly named access_rules_package in favor of role_assignment_module_package on NetworkConfigurationResponse.well_known_addresses. Obsoleted property will contain effective copy of the new one for backwards compability.

1.3.0

Release built: 29.01.2024

Adds support for protocol updates (in general) and the anemone update in particular.

API Changes

• Adds support for a new transaction type (flash transactions) that occur during protocol updates.
• Extends well known addresses returned from /status/network-configuration to include the transaction tracker address.
• DEPRECATION - Obsoletes the vm_type, code_hash_hex and code_hex properties of StateEntityDetailsResponsePackageDetails in favor of the codes collection. With the upcoming protocol upgrade it will be possible to have multiple codes per package. The obsoleted properties will contain an effective copy of the first element of the new collection for backwards compability.

Database changes

• Moves vm_type to package_code_history table from package in entity table.
• Creates new package_blueprint_aggregate_history table which will hold pointers to all package blueprints.
• Creates new package_code_aggregate_history table which will hold pointers to all package codes.

1.2.5

Release built: 26.01.2024

• Fixed broken (incompatible) Core API SDK

1.2.4

Release built: 4.01.2024

... (truncated)

• 9760898 Merge pull request #646 from radixdlt/release/babylon-1.4.0
• a0d1eb2 escape types in docs.
• c12b446 update redocly docs how to query kv store.
• 7c90d59 update compose with newest images and add put release date in changelog.
• 4255ed9 regenerate typescript sdk.
• 4829f19 Merge pull request #648 from radixdlt/validator-uptime-idx
• 23b2028 Merge pull request #647 from radixdlt/strict-ledger-state
• f4d94a9 Use strict at_ledger_state.state_version and from_ledger_state.state_version ...
• 7ee04a5 Changed ValidatorEmissionStatistics index to improve performance of `GetVal...
• 712cf67 Merge pull request #643 from radixdlt/new-endpoint-to-iterate-key-value-store
• Additional commits viewable in compare view

You can trigger Dependabot actions by commenting on this PR:

• @dependabot rebase will rebase this PR
• @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
• @dependabot merge will merge this PR after your CI passes on it
• @dependabot squash and merge will squash and merge this PR after your CI passes on it
• @dependabot cancel merge will cancel a previously requested merge and block automerging
• @dependabot reopen will reopen this PR if it is closed
• @dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
• @dependabot show <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency
• @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)